Release 10.1A: OpenEdge Deployment:
Managing 4GL Applications

Building a customized executable on UNIX

This section contains instructions for building 4GL client or AppServer™ executables running under UNIX to access custom C functions. The OEBuild script is located in the oebuild/make directory under the root of your OpenEdge installation.

To build a UNIX 4GL client executable:

Open a terminal and invoke a Bourne shell (/bin/sh) on the system where OpenEdge is installed.
Change to user root.
Run the PROENV utility to set the DLC variable. For example:

>$DLC/bin/proenv

Optionally set and export the environment variable IMAGE to the full pathname of the executable to be generated. For example:

proenv> IMAGE=/tmp/_myprogres proenv> export IMAGE

Note: By default, the custom client executable is named $DLC/oebuild/_progres if you are building the 4GL client (or WebSpeed agent) executable. It is $DLC/oebuild/_proapsv if you are building the AppServer agent executable.
Make sure that the environment variable PATH contains the directory to the supported compiler and linker on your system.
Unset all the library path variables for your operating system. The script will set these variables as required. For example, on HP-UX:

proenv> unset SHLIB_PATH

Make a backup copy of the original OEBuild link options script and the 4GL tie-in object used to access custom C functions, hlprodsp.o. There are two versions of the OEBuild link options script, depending on the 4GL client executable you plan to build:
build_rx.sh — 4GL client (or WebSpeed® agent) executable.
build__proapsv.sh — AppServer agent executable.

For example, to copy the original 4GL client and 4GL tie-in object:

proenv> cp $DLC/oebuild/make/build_rx.sh            $DLC/oebuild/make/build_rx.sh.orig proenv> cp $DLC/oebuild/obj/hlprodsp.o $DLC/oebuild/obj/hlprodsp.o.orig

Edit the C source file for the 4GL tie-in object in order to tie in your C functions to the 4GL as explained in the source file comments. This file is located at the following path:

$DLC/oebuild/hlc/hlprodsp.c

Compile the new tie-in object. For example:

proenv> cc -c -o $DLC/oebuild/hlc/hlprodsp.o $DLC/oebuild/hlc/hlprodsp.c

Set and export the environment variable HLC_OBJS to contain the paths of all objects that need to be included in your new OpenEdge executable, including the 4GL tie-in object you built in Step 9. For example:

proenv> HLC_OBJS="/home/foo.o /home/foo1.o $DLC/oebuild/hlc/hlprodsp.o" proenv> export HLC_OBJS

Run the OEBuild script located in $DLC/oebuild/make, with no arguments. There are two versions of the OEBuild script, depending on the 4GL client executable you plan to build:
build_rx.sh — 4GL character client (or WebSpeed® agent) executable.
build__proapsv.sh — AppServer agent executable.

For example, to build a customized character client:

proenv> $DLC/oebuild/make/build_rx.sh

Note: If you do not set the IMAGE variable, as in Step 4, the client executable is built as $DLC/oebuild/_progres for the 4GL character client agent or $DLC/oebuild/_proapsv for the AppServer agent; otherwise, the executable is built as specified by $IMAGE.